Evergreen notes should be atomic.
Notebooks are
write about one thing only.
However, as much as possible
Write so that the whole picture of the matter can be grasped.
is best
nishio.iconNote that only the "write only about one matter" part is widespread, but this means "it is best to be able to do both" since it indicates two conditions in one sentence, and it is not best to do the former at the expense of the latter.
He explains below that too much breadth has these disadvantages, and too much fragmentation has these disadvantages.
That balance is important.
nishio.icon2023-10-06 The boundary of "one" is not self-evident since it is innumerable to begin with If the note is too wide,
Difficulty in noticing when you come across a related new idea for one of the multiple ideas in the notebook
Also, the link to that note is ambiguous.
nishio.iconThis seems to implicitly assume that a link to a note leads to the beginning of that note
Scrapbox's ability to scroll to a line link or link position would allow me to point to that part of the page even if multiple thoughts are on one page.
If you're doing a line link instead of linking by the title itself, that means that something different from the title must be written from that line. Related.
He said the notes are too fragmented,
The link network is also fragmented.
It is difficult to see some of the connections.
There is no clear indicator or correct answer here, but rather a trade-off.
This concept is very similar to the principle of "separation of interests (separation of concerns)" in software engineering. In this principle, the module should be "about one thing only",
The company states that this would facilitate reuse.
However, if the pages are subdivided too much, the cohesion problem (cohesion problem) arises, just as it does if the modules are subdivided too much. nishio.iconSimply put, the more detailed the division, the greater the amount of intervening material.
In the source code, there are more import statements, more communication between servers if they are divided into multiple servers, etc.
nishio.iconBasically, the more you subdivide a module, the more overhead there is at the joints, and the worse the performance gets.
This is especially true for physical products, a topic well-studied in the field of business administration
---
This page is auto-translated from /nishio/常緑のノートはアトミックであるべき using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.